The Action Recorder is designed to be intuitive and allow you to create custom commands that can reduce the number of actions required to perform a repetitive task. There are some things to consider when recording an action macro.
When recording an action macro, you should be aware of the following:
| ACTSTOP | ACTUSERINPUT |
| ACTUSERMESSAGE | -ACTUSERMESSAGE |
| DXFIN | EXPORTLAYOUT |
| FILEOPEN | NEW |
| OPEN | PARTIALOPEN |
| PRESSPULL | QNEW |
| RECOVER | TABLEDIT |
| VBAIDE | -VBALOAD |
| VBALOAD | VBAMAN |
| VBANEW | VBAPREF |
| -VBARUN | VBARUN |
| VBASTMT | VBAUNLOAD |
| XOPEN | ACTBASEPOINT |
| ACTMANAGER |
Some of the user interface elements that start commands are: most tools on tool palettes, some actions in DesignCenter, and some tools on the status bars.
When editing an action macro, the action macro files that are found in the paths defined by the system variables ACTRECPATH and ACTPATHare loaded. If more than one action macro file has the same name, the first action macro file that is found is loaded into the Action Recorder. The other files with the same names are ignored and not loaded.
To identify the path of a loaded action macro, select the action macro from the Action Macros drop-down list and expand the Action Recorder panel. Right-click the action macro’s node in the Action tree and click Properties. In the Action Macro dialog box, the path to the action macro file is displayed in the Folder Path text box.
When playing back an action macro, you should be aware of the following:
When exchanging action macros with others, you should be aware of the following: